Tree preservation zone

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

entity: 19206817

reference: 6812
name
tree-preservation-order: undefined
Multiple Addresses Include Elmdene, Oakdene Drive, Raleigh Drive, Southwood Drive, Warren Drive South, Meadway
tree-preservation-zone-type: T
geometry: MULTIPOLYGON (((-0.271890 51.384835,-0.271882 51.384837,-0.271879 51.384841,-0.271882 51.384847,-0.271887 51.384849,-0.271893 51.384849,-0.271900 51.384845,-0.271901 51.384843,-0.271900 51.384839,-0.271896 51.384836,-0.271890 51.384835)))
point: POINT (-0.27189 51.384842)
notes
entry-date: 2025-03-18
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Royal Borough of Kingston upon Thames’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL